Re: [Emc-users] Thoughts on a Python script to calculate estimated run time, for G code and my first hacked sub routine

[Frank Tkalcevic]

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.

Frank 





> -Original Message-
> From: Sebastian Kuzminsky [mailto:s...@highlab.com]
> Sent: Thursday, 9 October 2014 1:45 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
> 
> 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, the estimate is off.  It's based on the gcode only, and does not take
into
> account important things like machine acceleration and spindle
acceleration
> as you say, as well as things like tolerance (G64 P) and probing.
> 
> The only way I can think of to improve the estimate would be to run the
> motion controller, disconnected from actual motion, and see how long the
> motion actually takes.  That's probably possible, but it's not a small
change to
> design & implement.
> 
> 
> --
> Sebastian Kuzminsky
> 
>

--
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve
> PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you
> Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to
> PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.cl
> ktrk
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
class AxisParam:
def __init__(self, vel, acc):
self.vel = vel
self.acc = acc

def StraightExecutionTime( self, distance, feedrate ):

t = 0.0
if feedrate is None:
v = self.vel
elif feedrate > self.vel:
v = self.vel
else:
v = feedrate

distance = abs(distance)
a = self.acc

if distance > 0:
# calc time and distance to accelerate to v
# v = at
# s = 1/2 a t^2 + v0 t,  assume v0 = 0
t = v / a
s =  1.0 / 2.0 * a * t *t

# check if accelerating to v then decelerating to v fits in the 
distance
if 2.0*s < distance:
t = 2.0 * t + (distance - 2.0*s) / v
else:
t = 2.0*math.sqrt( 2.0 * (distance/2.0) / a )

#print "distance=",distance, "a=", a, "v=", v, "t=", t
return t

def CalcExecutionTime( axis_params, start_point, end_point, feedrate=None ):
distance = sum( (s-e)**2 for s, e in zip(start_point, end_point))
distance = math.sqrt(distance)

longest_time = 0
for ap,start,end in zip(axis_params, start_point, end_point ):
if not ap is None:
f = feedrate
if not feedrate is None:
f = feedrate * abs(end-start)/distance
time = ap.StraightExecutionTime( end - start, f )
if time > longest_time:
longest_time = time
return longest_time

def CalcArcExecutionTime( ap, arcfeed ):
# Arcs have already been converted into line segments.
# We calculate absolute distance travelled in dx, dy, dz, etc
# and estimate the time in each axis.  This wont take into
# account an axis with low acceleration, but should be close enough.
time = 0
last_line = 0
last_feed = 0
arclen = [0,]*9
segcount = 0
for arcseg in arcfeed:
# Each record contains, line number, start, end, feedrate.
# We determine the end of an arc when the line # changes or the feed 
changes
line = arcseg[0]
start = arcseg[1]
end = arcseg[2]
feed = arcseg[3]

if line != last_line or feed != last_feed:
if segcount > 0:
t = CalcExecutionTime( ap, [0,]*9, arclen, last_feed )
time += t

arclen = [0,]*9
segcount = 0

# sum the distance travelled in each axis
for i in range(0,9):
arclen[i] += abs(end[i]-start[i])
segcount += 1

last_feed = feed
last_line = line

if segcount > 0:
t = CalcExecutionTime( ap, (0,)*9, arclen, last_feed )
time += t

return time

#

Re: [Emc-users] Thoughts on a Python script to calculate estimated run time, for G code and my first hacked sub routine

[Sebastian Kuzminsky]

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

Re: [Emc-users] Thoughts on a Python script to calculate estimated run time, for G code and my first hacked sub routine

[Todd Zuercher]

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" 
To: "Enhanced Machine Controller (EMC)" 
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

[Emc-users] OT: Pogo Pins

[Kirk Wallace]

I'm planning on using these pins: http://www.ebay.com/itm/141233257616
which are .053" in dia. with 5mm and .150" pitch.

I would like to connect to the pogos with a connector rather than 
soldering a wire. I would like the connector to be between two boards:
http://wallacecompany.com/tmp/Screenshot_pogo1.png

I recall some connectors used to connect board to board, where header 
pins from the bottom board pass through the bottom of the top board and 
into a connector on top. Does anyone have a link to such connectors?

-- 
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/

--
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

Re: [Emc-users] Thoughts on a Python script to calculate estimated run time, for G code and my first hacked sub routine

[Karlsson & Wang]

How about running the actual machine empty for one cycle?

Nicklas Karlsson



On Wed, 15 Oct 2014 21:07:28 +1100
"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.
> 
> Frank 
> 
> 
> 
> 
> 
> > -Original Message-
> > From: Sebastian Kuzminsky [mailto:s...@highlab.com]
> > Sent: Thursday, 9 October 2014 1:45 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
> > 
> > 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, the estimate is off.  It's based on the gcode only, and does not take
> into
> > account important things like machine acceleration and spindle
> acceleration
> > as you say, as well as things like tolerance (G64 P) and probing.
> > 
> > The only way I can think of to improve the estimate would be to run the
> > motion controller, disconnected from actual motion, and see how long the
> > motion actually takes.  That's probably possible, but it's not a small
> change to
> > design & implement.
> > 
> > 
> > --
> > Sebastian Kuzminsky
> > 
> >
> 
> --
> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve
> > PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you
> > Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to
> > PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.cl
> > ktrk
> > ___
> > 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

Re: [Emc-users] OT: Pogo Pins

[Stephen Dubovsky]

Could you use a tag cable? (there are other sources of the same thing.)  We
use them for programming.
http://www.tag-connect.com/

Samtec makes header sockets that can come up through the bottom of the
board.  We use those too.

SMD

On Wed, Oct 15, 2014 at 3:50 PM, Kirk Wallace 
wrote:

> I'm planning on using these pins: http://www.ebay.com/itm/141233257616
> which are .053" in dia. with 5mm and .150" pitch.
>
> I would like to connect to the pogos with a connector rather than
> soldering a wire. I would like the connector to be between two boards:
> http://wallacecompany.com/tmp/Screenshot_pogo1.png
>
> I recall some connectors used to connect board to board, where header
> pins from the bottom board pass through the bottom of the top board and
> into a connector on top. Does anyone have a link to such connectors?
>
> --
> Kirk Wallace
> http://www.wallacecompany.com/machine_shop/
> http://www.wallacecompany.com/E45/
>
>
> --
> 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

Re: [Emc-users] OT: Pogo Pins

[John Kasunich]

I'm not sure exactly what you are aiming for, but I did something a little
while ago that I think is very similar.

I got the sockets that the pins fit into.  They have a step in the outside
diameter.  I laid out the upper board with holes that the entire socket
fits thru, and the lower board with holes that only the lower part of the
socket fits thru.  Mounted the boards to each other with spacers, etc.
Then inserted the sockets from the top.  The socket goes in until the
step hits the lower board.  Then I soldered to both boards and inserted
the pogo pins into the sockets.

Obviously that won't work if you need to separate the two boards.

The pins I used are Mouser 855-P25-1223 (Harwin P25-1223)
The sockets are Mouser 855-S25-512 (Harwin S25-512)

Drawings for both are available at the Mouser website.
http://www.mouser.com/ds/2/181/P25-XX23-350405.pdf
http://www.mouser.com/ds/2/181/S25-XX2-351647.pdf

Buying the probes from Mouser is quite a bit more expensive than 
from ebay.  It didn't matter in my case - it was for work and I only
needed a modest number, a reliable source of supply was more
important.

But the Harwin probes are also 0.053 diameter - I think that is an
industry standard.  You could probably use the Harwin/Mouser
sockets with your ebay pins.  Or maybe find similar sockets on
ebay?

 On Wed, Oct 15, 2014 at 3:50 PM, Kirk Wallace 
 wrote:
 
 > I'm planning on using these pins: http://www.ebay.com/itm/141233257616
 > which are .053" in dia. with 5mm and .150" pitch.
 >
 > I would like to connect to the pogos with a connector rather than
 > soldering a wire. I would like the connector to be between two boards:
 > http://wallacecompany.com/tmp/Screenshot_pogo1.png
 >
 > I recall some connectors used to connect board to board, where header
 > pins from the bottom board pass through the bottom of the top board and
 > into a connector on top. Does anyone have a link to such connectors?
 >
 > --

-- 
  John Kasunich
  jmkasun...@fastmail.fm

--
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

Re: [Emc-users] OT: Pogo Pins

[John Kasunich]

I just remembered that I had a detailed drawing of what I did. A
picture is worth a thousand words.  See attached.

This was a test fixture for a small PC board.  The main part of
the fixture was a board on the bottom, with short pins that 
contacted the back of the board under test.  The pogo pins 
are part of a separate assembly that goes over the top and
serves the dual purpose of pushing the UUT down onto the
lower pins and contacting a couple connectors on the top
of the UUT.  Not shown are pan-head screws that hold
the upper-most board to the male-female standoffs.


On Wed, Oct 15, 2014, at 04:42 PM, John Kasunich wrote:
> I'm not sure exactly what you are aiming for, but I did something a little
> while ago that I think is very similar.
> 
> I got the sockets that the pins fit into.  They have a step in the outside
> diameter.  I laid out the upper board with holes that the entire socket
> fits thru, and the lower board with holes that only the lower part of the
> socket fits thru.  Mounted the boards to each other with spacers, etc.
> Then inserted the sockets from the top.  The socket goes in until the
> step hits the lower board.  Then I soldered to both boards and inserted
> the pogo pins into the sockets.
> 
> Obviously that won't work if you need to separate the two boards.
> 
> The pins I used are Mouser 855-P25-1223 (Harwin P25-1223)
> The sockets are Mouser 855-S25-512 (Harwin S25-512)
> 
> Drawings for both are available at the Mouser website.
> http://www.mouser.com/ds/2/181/P25-XX23-350405.pdf
> http://www.mouser.com/ds/2/181/S25-XX2-351647.pdf
> 
> Buying the probes from Mouser is quite a bit more expensive than 
> from ebay.  It didn't matter in my case - it was for work and I only
> needed a modest number, a reliable source of supply was more
> important.
> 
> But the Harwin probes are also 0.053 diameter - I think that is an
> industry standard.  You could probably use the Harwin/Mouser
> sockets with your ebay pins.  Or maybe find similar sockets on
> ebay?
> 
>  On Wed, Oct 15, 2014 at 3:50 PM, Kirk Wallace 
>  wrote:
>  
>  > I'm planning on using these pins: http://www.ebay.com/itm/141233257616
>  > which are .053" in dia. with 5mm and .150" pitch.
>  >
>  > I would like to connect to the pogos with a connector rather than
>  > soldering a wire. I would like the connector to be between two boards:
>  > http://wallacecompany.com/tmp/Screenshot_pogo1.png
>  >
>  > I recall some connectors used to connect board to board, where header
>  > pins from the bottom board pass through the bottom of the top board and
>  > into a connector on top. Does anyone have a link to such connectors?
>  >
>  > --
> 
> -- 
>   John Kasunich
>   jmkasun...@fastmail.fm
> 
> --
> 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


-- 
  John Kasunich
  jmkasun...@fastmail.fm


tester-scratch.pdf
Description: Adobe PDF document
--
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

Re: [Emc-users] OT: Pogo Pins

[Kirk Wallace]

On 10/15/2014 02:06 PM, John Kasunich wrote:
> I just remembered that I had a detailed drawing of what I did. A
> picture is worth a thousand words.  See attached.

... snip

Thank you Dennis and John. I didn't realize the pins are meant to be 
used with sockets. The sockets offer some flexibility. The example pin 
beds I have found on the Net have used vero(?) boards which have .1" 
spacing, but the spacing I need is 5mm and .15" and I don't have time to 
make up a custom PC board. The sockets seem to have a ring and step I 
can use instead of fixing with solder.


-- 
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/

--
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

Re: [Emc-users] OT: Pogo Pins

[Jon Elson]

On 10/15/2014 02:50 PM, Kirk Wallace wrote:
> I'm planning on using these pins: http://www.ebay.com/itm/141233257616
> which are .053" in dia. with 5mm and .150" pitch.
>
> I would like to connect to the pogos with a connector rather than
> soldering a wire. I would like the connector to be between two boards:
> http://wallacecompany.com/tmp/Screenshot_pogo1.png
These pins on eBay ore only half of the set.  I buy mine 
from Newark, there are
several versions of the socket end of the set.  I use the 
ones with wire-wrap pins
on the back end.
> I recall some connectors used to connect board to board, where header
> pins from the bottom board pass through the bottom of the top board and
> into a connector on top. Does anyone have a link to such connectors?
>
These pins are made for testing PC boards after assembly.  
They are not designed for
long-term operation in systems.  I am not sure the tip of 
the pins can be expected to
make long-term good contacts to a PC board.

Jon

--
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

[Emc-users] Axis GUI in 2.6.3 missing the Machine Velocity display ?

[Dave Cole]

The Axis Gui somewhere along the way lost the Machine Velocity display 
apparently?

I think it might still be there but it may be black text on a black 
background.

Does anyone have an idea how to fix this?

Under View, there is a show/don't show Machine Velocity selection, but 
it doesn't work.


Dave



---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com


--
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

Re: [Emc-users] Thoughts on a Python script to calculate estimated run time, for G code and my first hacked sub routine

[Gene Heskett]

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 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 haven't played with that one for a while, but that estimated time of 
3.44 is still way faster that it will run cutting air on my machine.  
Estimated time is 13.3 minutes on my machine (without these patches, most 
recent 2.6.3 install), cutting air runtime was 14:30 at the speed limits 
of my toy just now.  Fairly close IOW.

I actually made that in a 2x6x6 block of pine, years ago, and would have 
done it in maple if it looked good, but because of the limited length of 
the flutes of my mill, had to do 3 passes to get to full depth.  I had 
bookends in mind, but in pine it was at best "so ugly its pretty". :)

My point is that the simulator, a 2.7.pre build, does run faster here, 
noticeably faster.
 
> 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.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

--
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

Re: [Emc-users] Thoughts on a Python script to calculate estimated run time, for G code and my first hacked sub routine

[Frank Tkalcevic]

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" 
> To: "Enhanced Machine Controller (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

Re: [Emc-users] OT: Pogo Pins

[Gene Heskett]

On Wednesday 15 October 2014 17:06:57 John Kasunich did opine
And Gene did reply:
> I just remembered that I had a detailed drawing of what I did. A
> picture is worth a thousand words.  See attached.
> 
> This was a test fixture for a small PC board.  The main part of
> the fixture was a board on the bottom, with short pins that
> contacted the back of the board under test.  The pogo pins
> are part of a separate assembly that goes over the top and
> serves the dual purpose of pushing the UUT down onto the
> lower pins and contacting a couple connectors on the top
> of the UUT.  Not shown are pan-head screws that hold
> the upper-most board to the male-female standoffs.
> 
> On Wed, Oct 15, 2014, at 04:42 PM, John Kasunich wrote:
> > I'm not sure exactly what you are aiming for, but I did something a
> > little while ago that I think is very similar.
> > 
> > I got the sockets that the pins fit into.  They have a step in the
> > outside diameter.  I laid out the upper board with holes that the
> > entire socket fits thru, and the lower board with holes that only
> > the lower part of the socket fits thru.  Mounted the boards to each
> > other with spacers, etc. Then inserted the sockets from the top. 
> > The socket goes in until the step hits the lower board.  Then I
> > soldered to both boards and inserted the pogo pins into the sockets.
> > 
> > Obviously that won't work if you need to separate the two boards.
> > 
> > The pins I used are Mouser 855-P25-1223 (Harwin P25-1223)
> > The sockets are Mouser 855-S25-512 (Harwin S25-512)
> > 
> > Drawings for both are available at the Mouser website.
> > http://www.mouser.com/ds/2/181/P25-XX23-350405.pdf
> > http://www.mouser.com/ds/2/181/S25-XX2-351647.pdf
> > 
> > Buying the probes from Mouser is quite a bit more expensive than
> > from ebay.  It didn't matter in my case - it was for work and I only
> > needed a modest number, a reliable source of supply was more
> > important.
> > 
> > But the Harwin probes are also 0.053 diameter - I think that is an
> > industry standard.  You could probably use the Harwin/Mouser
> > sockets with your ebay pins.  Or maybe find similar sockets on
> > ebay?
> > 
> >  On Wed, Oct 15, 2014 at 3:50 PM, Kirk Wallace
> >  
> >  
> >  wrote:
> >  > I'm planning on using these pins:
> >  > http://www.ebay.com/itm/141233257616 which are .053" in dia. with
> >  > 5mm and .150" pitch.
> >  > 
> >  > I would like to connect to the pogos with a connector rather than
> >  > soldering a wire. I would like the connector to be between two
> >  > boards: http://wallacecompany.com/tmp/Screenshot_pogo1.png
> >  > 
> >  > I recall some connectors used to connect board to board, where
> >  > header pins from the bottom board pass through the bottom of the
> >  > top board and into a connector on top. Does anyone have a link to
> >  > such connectors?
> >  > 
> >  > --

John, the connector on the DUT board, in red in that .pdf, a "molex" part 
I have to assume although there are probably other makers, is, if used for 
board interconnect in the real world, is a time bomb with about a 1 year 
length fuse.  When its mating connector is used to mount a daughter pcb, 
the pressure from the retaining lip beside the pins is so great that no 
known solder, or trace pad size can prevent its ripping the puddle of 
solder and the trace loose on both faces of the DUT board, causing a loss 
of connection it take a strong glass to find.  I had to do so many repairs 
to that scheme in a HiGain 623 radio I owned for many years, that I 
eventually took my soldering iron and made a hell of a mess of a tip, 
burning away the nylon retaining lip, both on the motherboard and on the 
daughterboard.  End of problem. I wish I hadn't traded it off for a 
computer all those years ago.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

--
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

Re: [Emc-users] OT: Pogo Pins

[Frank Tkalcevic]

I just used a standard IDC connector and a bit of PCB to keep the 0.1"
spacing...

http://www.franksworkshop.com.au/images/pogo_icp.jpg



> -Original Message-
> From: Kirk Wallace [mailto:kwall...@wallacecompany.com]
> Sent: Thursday, 16 October 2014 6:51 AM
> To: Enhanced Machine Controller (EMC)
> Subject: [Emc-users] OT: Pogo Pins
> 
> I'm planning on using these pins: http://www.ebay.com/itm/141233257616
> which are .053" in dia. with 5mm and .150" pitch.
> 
> I would like to connect to the pogos with a connector rather than
soldering a
> wire. I would like the connector to be between two boards:
> http://wallacecompany.com/tmp/Screenshot_pogo1.png
> 
> I recall some connectors used to connect board to board, where header pins
> from the bottom board pass through the bottom of the top board and into a
> connector on top. Does anyone have a link to such connectors?
> 
> --
> Kirk Wallace
> http://www.wallacecompany.com/machine_shop/
> http://www.wallacecompany.com/E45/
> 
>

--
> 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