yes, but that's unrelated to the motion/task interface
it's about removing an NML limitation and provide late binding of shared
variables; this will be mostly for interp,task,ui, maybe HAL comps.
-m
Am 27.01.2012 um 22:55 schrieb andy pugh:
> On 27 January 2012 21:45, Kenneth Lerman wrote:
>
> From: bodge...@gmail.com
> Date: Fri, 27 Jan 2012 21:23:25 +
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] [Emc-users] question on gcode parsing
>
> On 27 January 2012 21:14, Kent A. Reed wrote:
> > (the next-generation next-generatio
On Fri, 27 Jan 2012 16:53:28 -0800 (PST)
"Peter C. Wallace" wrote:
> On Fri, 27 Jan 2012, andy pugh wrote:
>
> > Date: Fri, 27 Jan 2012 21:23:25 +
> > From: andy pugh
> > Reply-To: EMC developers
> > To: EMC developers
> > Subject: Re:
On Fri, 27 Jan 2012, andy pugh wrote:
> Date: Fri, 27 Jan 2012 21:23:25 +
> From: andy pugh
> Reply-To: EMC developers
> To: EMC developers
> Subject: Re: [Emc-developers] [Emc-users] question on gcode parsing
>
> On 27 January 2012 21:14, Kent A. Reed wrote:
>>
On 27 January 2012 21:45, Kenneth Lerman wrote:
> That's an implementation detail. I'd state it as a requirement. The
> inter-module interfaces shall be documented and "as simple as possible,
> but no simpler."
I can't claim to understand the technicalities, but I think that
mhaberler is thinkin
On 1/27/2012 4:23 PM, andy pugh wrote:
> On 27 January 2012 21:14, Kent A. Reed wrote:
>> (the next-generation next-generation controller?).
> The wish-list for that, for me, would include a reversible,
> jerk-limited, pause-and-resumable motion system.
You've stated the above as requirements.
> I
Hi Kent,
Thanks for setting me straight on that.
On the question you raise further down, I think that this would
represent a new branch. It would require significant changes to: motion
control, interpreter, GUIs.
Ken
On 1/27/2012 4:14 PM, Kent A. Reed wrote:
> On 1/27/2012 8:52 AM, Kenneth Le
On 27 January 2012 21:14, Kent A. Reed wrote:
> (the next-generation next-generation controller?).
The wish-list for that, for me, would include a reversible,
jerk-limited, pause-and-resumable motion system.
I think I would keep most of the rest of it, but the inter-module
communications seems ba
On 1/27/2012 8:52 AM, Kenneth Lerman wrote:
> <...>
>
> All of this stuff needs to be designed in; it can't be patched into the
> existing system.
>
> It's important to remember that the architecture and design of EMC is
> ancient in computer years. My guess is that it dates back to the early
> da
On 1/26/2012 5:36 PM, Michael Haberler wrote:
. Lots of good stuff snipped.
> re jog forwards/backwards:
> I'd be interested to hear your ideas in more detail. It comes up regularly in
> different shapes or forms, and it occurs to me that would need motion
> support. How can the
On Thu, 26 Jan 2012 18:54:35 -0500
"Kent A. Reed" wrote:
> On 1/26/2012 6:20 PM, dave wrote:
> > On Thu, 26 Jan 2012 14:33:10 -0500
> > "Kent A. Reed" wrote:
> >
> >> On 1/26/2012 6:32 AM, andy pugh wrote:
> >>> On 25 January 2012 21:44, Kenneth
> >>> Lerman wrote:
> >>>
> If this were ol
On Thu, 26 Jan 2012 20:42:03 -0500
Ron Bean wrote:
> dave writes:
>
> >A couple of years ago I tried the APT software on the wiki
>
> Is this what you're talking about?
>
> http://sourceforge.net/projects/aptos/
>
> Or something else?
>
Good grief! It was long enough ago that I had to go t
dave writes:
>A couple of years ago I tried the APT software on the wiki
Is this what you're talking about?
http://sourceforge.net/projects/aptos/
Or something else?
--
Try before you buy = See our experts in action
On 1/26/2012 6:20 PM, dave wrote:
> On Thu, 26 Jan 2012 14:33:10 -0500
> "Kent A. Reed" wrote:
>
>> On 1/26/2012 6:32 AM, andy pugh wrote:
>>> On 25 January 2012 21:44, Kenneth
>>> Lerman wrote:
>>>
If this were old style code (XA YB) it would not be valid because
it contains two lette
On Thu, 26 Jan 2012 14:33:10 -0500
"Kent A. Reed" wrote:
> On 1/26/2012 6:32 AM, andy pugh wrote:
> > On 25 January 2012 21:44, Kenneth
> > Lerman wrote:
> >
> >> If this were old style code (XA YB) it would not be valid because
> >> it contains two letters in a row. By eliminating the early
> >
Am 25.01.2012 um 22:27 schrieb Kenneth Lerman:
> On 1/25/2012 3:22 PM, Michael Haberler wrote:
>> [this should move to emc-developers, which is why I'm cc'ing there]
>>
>> it just occured to me that a decent parser would give us the opportunity for
>> a significant language simplification while
On 1/26/2012 6:32 AM, andy pugh wrote:
> On 25 January 2012 21:44, Kenneth Lerman wrote:
>
>> If this were old style code (XA YB) it would not be valid because it
>> contains two letters in a row. By eliminating the early whitespace removal,
>> 'XA YB' and 'AXYB' would mean two different things.
On 25 January 2012 21:44, Kenneth Lerman wrote:
> If this were old style code (XA YB) it would not be valid because it contains
> two letters in a row. By eliminating the early whitespace removal, 'XA YB'
> and 'AXYB' would mean two different things. 'X 123' and 'X123' would still be
> interpr
On 1/25/2012 4:33 PM, andy pugh wrote:
> On 25 January 2012 21:27, Kenneth Lerman wrote:
>
>> We should eliminate the removal of whitespace and use whitespace
>> as a delimiter.
> I am not sure that is necessarily a good idea, as a lot of G-code out
> there is space-free.
> Or am I misunderstand
On 25 January 2012 21:27, Kenneth Lerman wrote:
> We should eliminate the removal of whitespace and use whitespace
> as a delimiter.
I am not sure that is necessarily a good idea, as a lot of G-code out
there is space-free.
Or am I misunderstanding the point?
--
atp
The idea that there is no
On 1/25/2012 3:22 PM, Michael Haberler wrote:
> [this should move to emc-developers, which is why I'm cc'ing there]
>
> it just occured to me that a decent parser would give us the opportunity for
> a significant language simplification while retaining backwards compatibility.
>
> An example for t
[this should move to emc-developers, which is why I'm cc'ing there]
it just occured to me that a decent parser would give us the opportunity for a
significant language simplification while retaining backwards compatibility.
An example for the current RS274NGC language with variable references,
22 matches
Mail list logo
