Yeah, I don't have the latest trajectory planner. 3d_chips was one of my test files and came out ok without G64 settings.
Any suggestions on how to estimate with G64? > -----Original Message----- > From: Todd Zuercher [mailto:zuerc...@embarqmail.com] > Sent: Thursday, 16 October 2014 3:16 AM > To: Enhanced Machine Controller (EMC) > Subject: Re: [Emc-users] Thoughts on a Python script to calculate estimated > run time, for G code and my first hacked sub routine > > My guess is the new tool planner's G64 settings are throwing off the > estimate. Try the real time with tighter G64 PXXX, and I suspect your results > will differ. > > ----- Original Message ----- > From: "Sebastian Kuzminsky" <s...@highlab.com> > To: "Enhanced Machine Controller (EMC)" <emc- > us...@lists.sourceforge.net> > Sent: Wednesday, October 15, 2014 12:00:38 PM > Subject: Re: [Emc-users] Thoughts on a Python script to calculate estimated > run time, for G code and my first hacked sub routine > > On 10/15/14 4:07 AM, Frank Tkalcevic wrote: > > I was so annoyed that the estimates for my 3d printing jobs were so > > far off (estimated 2 hours, took 8) that I modified the axis code. It > > looks at the Velocity and acceleration of each axis and tries to > > calculate a more accurate time. It only looks at moves - no G64 or > > probing. It isn't perfect, but much closer. > > > > The attached file is the changes - a new gcode_properties function and > > some additional routines. > > > > My version of linuxcnc is pretty old, so a diff or patch wouldn't be useful. > > That change looks good to me, thanks. > > I pasted all the parts of your file into appropriate-seeming places in axis.py, > and it runs, so that's good. But i think something's off with the estimate still. > > I did some testing with the sim/axis/axis config. > > Your code's estimate for the splash screen gcode is 2:09, which is within a > second of the measured runtime. The current version of Axis in the master > branch estimates "2.1 minutes", so they agree on this one. > > But the estimate for 3D_Chips.ngc is way off. The current master version of > Axis estimates 0:46, your code estimates 3:44, and measured runtime is 1:11. > So I think there's some work to do still. > > I pushed your updated version to git.linuxcnc.org as a branch called > 'seb/master/ftkalcevic-axis-estimate', for wider testing and in case you want > to refine the code. > > > -- > Sebastian Kuzminsky > > ---------------------------------------------------------------------------- -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > > ---------------------------------------------------------------------------- -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
