Re: [Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread Andrew
Sure, I attached the code. Thanks! 2015-03-09 15:26 GMT+02:00 sam sokolik sa...@empirescreen.com: Do you have a gcode snippet that would show this? thanks sam On 3/9/2015 8:12 AM, Andrew wrote: Hello, I found this bug a couple of months back and it hasn't disappeared since.

Re: [Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread sam sokolik
in sim lathe - I get about 5.5ipm... which seems right - feed/rev of .14mm = 1000rpm*(.14*.03937)=5.5ipm. Feed override seems to work also... (and changing the spindle rpm changes feed) sam On 3/9/2015 8:34 AM, Andrew wrote: Sure, I attached the code. Thanks! 2015-03-09 15:26 GMT+02:00

Re: [Emc-developers] New TP bugs?

2015-03-09 Thread Andrew
2015-03-09 2:59 GMT+02:00 Robert Ellenberg rwe...@gmail.com https://mail.google.com/mail/u/0/?view=cmfs=1tf=1to=rwe...@gmail.com: Sorry, I meant in this list of times: KMotionCNC - 2:59 NCStudio v5.5.60 - 3:12 EdingCNC - 3:47 Mach3 - 5:25 PlanetCNC - 11:24 Which test program was

Re: [Emc-developers] Google Summer of Code students wanted!

2015-03-09 Thread John Thornton
I tried to switch a tiny bit of Python code from Gtk2 to Gtk3 and ran into problems and errors that could not get resolved. It was quite frustrating to say the least. I even consulted this page: https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html JT On 3/8/2015 1:44 PM, Chris

Re: [Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread sam sokolik
Do you have a gcode snippet that would show this? thanks sam On 3/9/2015 8:12 AM, Andrew wrote: Hello, I found this bug a couple of months back and it hasn't disappeared since. Sim-lathe slows down on G2 G3 arcs. Say, the feed is 140mm/min, it moves 140 on the lines and it's limited to 60

Re: [Emc-developers] New TP bugs?

2015-03-09 Thread Jeff Johnson
I will get it out today Jeff Johnson john...@superiorroll.com Superior Roll Turning 734-279-1831 -Original Message- From: Andrew [mailto:pkm...@gmail.com] Sent: Monday, March 09, 2015 7:12 AM To: EMC developers Subject: Re: [Emc-developers] New TP bugs? 2015-03-09 2:59 GMT+02:00

Re: [Emc-developers] Google Summer of Code students wanted!

2015-03-09 Thread John Thornton
In Gedit you can make the tab key insert spaces... which is what I do. JT On 3/8/2015 10:25 AM, Kirk Wallace wrote: On 03/08/2015 06:47 AM, EBo wrote: I agree. The tab-stop debate/issues have caused no end of problems not only in LCNC but in every distributed source code project I have

[Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread Andrew
Hello, I found this bug a couple of months back and it hasn't disappeared since. Sim-lathe slows down on G2 G3 arcs. Say, the feed is 140mm/min, it moves 140 on the lines and it's limited to 60 on arcs. Exactly 60 mm/min. Feed override is ignored on arcs, but works for lines. G94, G95, G96, G97

Re: [Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread sam sokolik
this program does show difference between planes.. G17 vs g18.. G18 peaks at about 320ipm vs G17 peaks at about 540ipm.. I don't see an issue with feed override. sam On 03/09/2015 08:26 AM, sam sokolik wrote: Do you have a gcode snippet that would show this? thanks sam On 3/9/2015 8:12

Re: [Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread sam sokolik
100% feedrate override (I set linuxcnc to display metric.) http://electronicsam.com/images/KandT/testing/Screenshot%20from%202015-03-09%2009:09:59.png 50% feedrate override http://electronicsam.com/images/KandT/testing/Screenshot%20from%202015-03-09%2009:10:26.png sam On 03/09/2015 08:56 AM,

Re: [Emc-developers] Google Summer of Code students wanted!

2015-03-09 Thread Sebastian Kuzminsky
On 03/08/2015 12:44 PM, Chris Morley wrote: Date: Thu, 5 Mar 2015 21:21:13 -0700 From: s...@highlab.com To: emc-us...@lists.sourceforge.net; emc-developers@lists.sourceforge.net Subject: [Emc-developers] Google Summer of Code students wanted! Some possible projects are listed on the

Re: [Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread Andrew
Thanks Sam, What's wrong then? Can you try my config? (attached, just put it in your sim-axis folder) 2015-03-09 15:56 GMT+02:00 sam sokolik sa...@empirescreen.com https://mail.google.com/mail/u/0/?view=cmfs=1tf=1to=sa...@empirescreen.com : in sim lathe - I get about 5.5ipm... which seems

Re: [Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread Andrew
I still think there's a bug. Indeed, inch lathe config works well. But when I change inch to mm and increase the values accordingly - it behaves exactly as described in my first message. So this is rather inch-mm bug somewhere. 2015-03-09 16:13 GMT+02:00 sam sokolik sa...@empirescreen.com: 100%

Re: [Emc-developers] G18 arcs bug in 2.7+

2015-03-09 Thread sam sokolik
Yes - I think I am seeing it too. 20in/s^2 inch config works great but a 500mm/s^2 metric config doesn't.. sam On 3/9/2015 12:01 PM, Andrew wrote: I still think there's a bug. Indeed, inch lathe config works well. But when I change inch to mm and increase the values accordingly - it

Re: [Emc-developers] hal_glib.py does return wrong homing status when using gantrykins

2015-03-09 Thread Niemand Sonst
Hallo, I am still looking for a solution. It seems to be impossible to get the number of joints within hal_glib. I tried self.stat.axes witch does return [TRAJ]AXES value being 4 for an XYZY gantry, but will be 6 for a XYZC machine. Then I tried self.stat.axis[i][axisType as for a non used

Re: [Emc-developers] Google Summer of Code students wanted!

2015-03-09 Thread Chris Morley
Date: Mon, 9 Mar 2015 08:42:08 -0600 From: s...@highlab.com To: emc-developers@lists.sourceforge.net Subject: Re: [Emc-developers] Google Summer of Code students wanted! On 03/08/2015 12:44 PM, Chris Morley wrote: Date: Thu, 5 Mar 2015 21:21:13 -0700 From: s...@highlab.com To:

Re: [Emc-developers] Google Summer of Code students wanted!

2015-03-09 Thread Slavko Kocjancic
On 09. 03. 2015 00:49, Sebastian Kuzminsky wrote: On 03/08/2015 12:40 AM, Slavko Kocjancic wrote: From my point of view you hit all the troubles. -it needs little cleaning (I don't know what's wrong at all) -I really don't know how to edit documentation. I just pushed some code to master