On 07/19/2017 08:26 AM, Nicklas Karlsson wrote:
I have arrived at a point there I am starting to think about
splitting linuxcnc in two, one for real time and the other for GUI. I
know it have been up before not to long time ago. I guess move EMCMOT
and below is what I start with but EMCTASK I am a little bit unsure
about.
Do anybody have experience of suggestions for this?
LinuxCNC already is split this way, though in practice almost(?)
everyone runs the realtime part and the non-realtime part on the same
machine.
This diagram shows where the realtime/non-realtime split is:
http://linuxcnc.org/docs/2.7/html/code/code-notes.html#_architecture_overview
That diagram is a little outdated; it is from before HAL.
HAL spans the divide and lets realtime and non-realtime components talk
to each other easily.
HAL is currently not network-transparent, so components on one computer
can't make HAL net connections to components on a different computer.
This may or may not be an obstacle for your use case.
--
Sebastian Kuzminsky
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
