Hi from Brazil! It seems some developer at machinekit did some good work there. I tested this:. https://machinekoder.com/extending-machineface-with-hal-remote-to-control-smart-plugs/ years ago, and that worked pretty well. IMHO haltalk and machinetalk: https://machinekoder.com/machinetalk-explained-part-1-introduction/ are the best features in machinekit that are missing in linuxcnc.
Regards Daniel Em dom, 3 de mai de 2020 04:26, Reinhard <reinha...@schwarzrot-design.de> escreveu: > On Sonntag, 3. Mai 2020, 09:13:22 CEST N wrote: > > That said it might still make sense to have some kind of > > communication in between GUI and hal ... > > Yes! > > I'd like to implement my buttons in hardware, together with some potis and > currently I don't know, how to get rid of it from my gui. > I know, that halui handles all this, but I can't access halpins from > outside > of realtime. > I know, that i can create a component, that can be started by "loaduser", > which then is not a realtime task (and I already succeeded in doing so), > but I > don't know, how to communicate with processes started by halcmd from my > app. > > Shared memory without nml-handshake would be nice. > Then clients would not slow down halui - although I don't know about the > impact of nml-handshake. > > Reinhard > > > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers