At 03:27 PM 1/9/2009, you wrote:
>On Fri, Jan 09, 2009 at 08:06:18PM +, paul_c wrote:
> >
> > So what do *you* consider to be the "alternatives" capable of providing
> > similar functionality ?
>
>This thread is more appropriate for emc-developers. This list is
>crazy enough lately! Please pu
On Fri, Jan 09, 2009 at 08:06:18PM +, paul_c wrote:
>
> So what do *you* consider to be the "alternatives" capable of providing
> similar functionality ?
This thread is more appropriate for emc-developers. This list is
crazy enough lately! Please put any responses there.
On Thursday 08 January 2009, Alex Joni wrote:
> NML is the mechanism which is used for defining the dataset and
> communication paths between the various userspace components.
> If you look at the (slightly outdated) overview of EMC:
> * there were (every couple of years) talks about replacing it
Hi Richard,
sorry it took a while to reply...
> Could someone explain or point me to documentation that explains the
> following:
>
> 1.What does the motion controller do? Is is part of HAL? How is it
> built? I see that the file motion.c has a 'main' function but the
> Makefile does not link it,
On Thursday 08 January 2009, Kenneth Lerman wrote:
> For my use and for (as far as I can tell), almost everyone else, it is
> unnecessary.
NML describes the data structures as well as the methods for transmitting the
PODs to the various parts of EMC - *Everyone* uses it. Even within the task
pla
For my use and for (as far as I can tell), almost everyone else, it is
unnecessary. It is also complex.
Ken
paul_c wrote:
> On Wednesday 07 January 2009, Kenneth Lerman wrote:
>> NML is used because it supports an environment where functions are split
>> across multiple machines.
>>
>> I don't k
On Wednesday 07 January 2009, Kenneth Lerman wrote:
> NML is used because it supports an environment where functions are split
> across multiple machines.
>
> I don't know how widely that functionality is used, though. As far as
> I'm concerned, it adds an unnecessary level of complexity.
Please d
I'll take a shot at answering number 3.
Richard F. Amaral wrote:
> Could someone explain or point me to documentation that explains the
> following:
...
>
> 3. Why use NML? Why not use just shared memory? Is NML an attempt at
> standardizing communication between software entities, i.e.
> u
Could someone explain or point me to documentation that explains the
following:
1.What does the motion controller do? Is is part of HAL? How is it
built? I see that the file motion.c has a 'main' function but the
Makefile does not link it, only compiles it to an object file. How is
this ob
