On Tue, 26 Mar 2019, andy pugh wrote:
Date: Tue, 26 Mar 2019 11:19:19 +0000 From: andy pugh <bodge...@gmail.com> Reply-To: "Enhanced Machine Controller (EMC)" <emc-users@lists.sourceforge.net> To: "Enhanced Machine Controller (EMC)" <emc-users@lists.sourceforge.net> Subject: Re: [Emc-users] Rock64 pre-orders on Banggood.On Tue, 26 Mar 2019 at 06:35, Chris Albertson <albertson.ch...@gmail.com> wrote:
The loops do need data. They need a target position or a target velocity. These targets are sent across an SPI (or I2C or Ethernet or,..) interface from a Linux machine. But you MUST de-couple the timing. Linux can not be feeding one target number at a time.
Drawing the boundary becomes more difficult when you add in probing, threading and spindle-synchronised motion.
Yes, if you have distributed controllers doing real time you have basically re-invented a buffered system like Mach3 with all its limitations.
Theres a reason most of these buffered systems have issues with threading, rigid tapping, probing, torch height control, adaptive feed, (or whatever new clever thing you want to do in real time)
Basically you substitute a complex buffered system model for the simple single locus of control that LinuxCNC has with HAL. Now its possible to move HAL to a remote device but for all of HALs features you need loadable modules and OS resources, (and realtime or course) so you basically end up running LinuxCNC on the remote device anyway...
Peter Wallace Mesa Electronics _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
