On Wednesday 15 October 2014 12:00:38 Sebastian Kuzminsky did opine
And Gene did reply:
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
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
On 10/16/14 12:22 AM, Frank Tkalcevic wrote:
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?
You'd need to duplicate the functionality of the trajectory planner to
get G64P
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
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
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)
How about running the actual machine empty for one cycle?
Nicklas Karlsson
On Wed, 15 Oct 2014 21:07:28 +1100
Frank Tkalcevic fr...@franksworkshop.com.au 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
Thanks John,
I will keep this in mind if i need to calculate run times more
precisely.
Just out of curiosity how dose LinuxCNC deal with sub routines, if, or,
wile, logic ect. I am assuming it reads ahead does the calculations and
spit out standard g code to the interpreter where it is
If you need the exact time to run a file create a simulator with the
same acceleration and velocity settings as your machine. Add the time
component to the simulator then run your file.
JT
On 10/8/2014 10:01 AM, Schooner wrote:
First Q
From Axis
File Properties
Brings up the
Hello
I have been reading along on this mailing list for a few weeks now
and playing with Linuxcnc Axis simulator in my free time. Both have been
very informative and I have learned a lot. There are two items I was
wondering if I could get a comment on.
#1 Dose any one have a python script
On Wednesday 08 October 2014 08:36:06 linden did opine
And Gene did reply:
Hello
I have been reading along on this mailing list for a few weeks now
and playing with Linuxcnc Axis simulator in my free time. Both have
been very informative and I have learned a lot. There are two items I
First Q
From Axis
File Properties
Brings up the properties of the currently loaded gcode including
estimated run time
Always underestimates as it takes no account of time used in
acceleration and deceleration to/from the required Feed speed
regards
On 10/8/14 9:01 AM, Schooner wrote:
First Q
From Axis
File Properties
Brings up the properties of the currently loaded gcode including
estimated run time
Always underestimates as it takes no account of time used in
acceleration and deceleration to/from the required Feed speed
Yep,
On Wednesday 08 October 2014 10:44:58 Sebastian Kuzminsky did opine
And Gene did reply:
On 10/8/14 9:01 AM, Schooner wrote:
First Q
From Axis
File Properties
Brings up the properties of the currently loaded gcode including
estimated run time
Always underestimates as it
Thanks Sebastian Shooner for the comments, and Gene for running my code,
The file properties estimation of run time is exactly what I was
looking for. I intend to use it for path optimization in my code rather
than job estimation. I am comparing code to code. The actual run time I
m not
On Wednesday 08 October 2014 18:21:06 linden did opine
And Gene did reply:
Thanks Sebastian Shooner for the comments, and Gene for running my
code,
The file properties estimation of run time is exactly what I was
looking for. I intend to use it for path optimization in my code rather
16 matches
Mail list logo
