Machinekit is a little bit up in the cloud they lack the blocks and signal paths. Linuxcnc have a better block diagram vith blocks and signal paths.
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?EMC_Components There is also a clear distinction which part are real time and in contrast to some other I do not consider user interface as real time. > >> GUI and possible EMCTASK should be possible to put on separate > >> devices. Someone told be me NML have been broken but fixed. The gui > >> is already there so if your device could run the code it should as > >> far as I understand be possible to split the application. > >> > >> I want to achieve something similar but this is because I want to > >> remove real time demand from user interface. It might also be useful > >> with more than one GUI and remote control. > > > > An additional complication with running the UI on a separate machine > > from the motion controller is that many (all?) UIs want to connect via > > both NML and HAL, and there's no good remote HAL interface currently. > > > > So you'd have to either write a GUI that doesn't use HAL, or write a > > remote HAL interface. > > Alexander Roessler just did a writeup about the remote HAL interface > implemented in Machinekit using ZeroMQ and Protobuf: > > http://machinekoder.com/machinetalk-explained-part-4-hal-remote/ ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
