ok - as you can see from my screen shot I was actually running 2.6.3
So - I actaully ran master and - it runs as expected... One of the
many small bugs fixed.. Yay Rob!!
http://electronicsam.com/images/KandT/testing/Screenshot%20from%202014-10-20%2015:02:29.png
sam
On 10/20/2014 02:
> From: viesturs.la...@gmail.com
> Date: Mon, 20 Oct 2014 20:48:42 +0300
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] incremental change to linuxcnc's APIs for user
> interfaces
>
> 2014-10-19 16:06 GMT+03:00 Jeff Epler :
> > Last night at the Texas fest, Chris Ra
Playing around with dxf2gcode.. (cool program btw..) It generated this
file (running in master)
http://electronicsam.com/images/KandT/testing/SPACOUT1.ngc
it violates the negative y acceleration on line 18,23,37 and so on.
http://electronicsam.com/images/KandT/testing/Screenshot%20from%202014
2014-10-19 16:06 GMT+03:00 Jeff Epler :
> Last night at the Texas fest, Chris Radek, Seb Kuzminsky, and I
> brainstormed an outline of an incremental way forward, which will take
> at least two releases before the ultimate goal of transitioning from NML
> to a different IPC method.
Is it just me w
On Oct 20 2014 3:37 AM, bruno wrote:
> it seems the poster want to create a new API to solve a problem which
> is
> already solved but needs a bit of work:
>
> - improve NML documentation
> - fix the NML library used by emcrsh, emclcd, etc. and their clients
> to
> use a different configuration f
On Mon, Oct 20, 2014 at 07:53:24PM +1100, Frank Tkalcevic wrote:
> I run axis on the local machine, then remote to it using keystick.
It also *typically* works when using e.g., axis + halui or axis +
linuxcncrsh.
However, sometimes it doesn't. This leads to reports like 328 (axis +
halui, using
On 20 October 2014 10:37, bruno wrote:
> NML seems very capable, might as well use it and fix the clients instead
> of creating a new architecture and associated bugs that will come with it.
As far as I know the Machinekit project is also trying to get rid of
NML (and might already have done so).
it seems the poster want to create a new API to solve a problem which is
already solved but needs a bit of work:
- improve NML documentation
- fix the NML library used by emcrsh, emclcd, etc. and their clients to
use a different configuration for each NML client
NML seems very capable, might as
> (The summary of those bugs is: the serial number method for UIs to ensure
a
> message is acted upon by task simply does not work when there is not just
> one UI. No simple modification will make it work, and no one in the
project
> in 10+ years has taken the time to understand NML with the depth
