> On Thu, Mar 24, 2016 at 08:54:56PM -0500, Jeff Epler wrote:
> > The work is on a branch, "[origin/]jepler/master/nml-tcp" and will not
> > make it into a release branch anytime soon.
>
> I changed my mind about this. The branch has now been merged into
> master, so nml-over-tcp may be a
> On Sun, Mar 20, 2016 at 04:51:39PM +, Ralph Stirling wrote:
> > The MachineKit folk are a year or two ahead of you guys
> > in thinking about the distributed control approach.
> [snip]
>
> The original "NIST EMC", a distant ancestor of LinuxCNC, already had a
> distributed control approach
In diagram there are first NML and then shared memory. If I put shared memory
buffer in micro controller it would talk NML with the EMCTASK.
> nml is the protocol/library between UIs and task, as well as between task
> and iocontrol. task (not realtime) uses a shared memory interface to
> talk
nml is the protocol/library between UIs and task, as well as between task
and iocontrol. task (not realtime) uses a shared memory interface to
talk to motion (realtime).
Jeff
--
Transform Data into Opportunity.
I read the diagram and EMCTASK is connected by NML:
First step would be to get it to work again.
Second to move lower parts to micro controller.
Then lower parts are on micro controller there is no need to care about real
time perfomance in GUI.
Are all NML communication paths via
