On Montag, 4. Mai 2020, 04:13:00 CEST Robert Murphy wrote: > I did come to realise that yes remote GUI would have a place in an > industrial setting.
May be I'm too simple minded. Could you please explain the conditions, where it makes sense to you? > I would imagine if the protocol was simple enough and with tcp a mid to > hi end microcontroller with a simple display could be put into use for > use in a hobby workshop. Could it be that it could function as an > extension of the GUI on the Linuxcnc machine, a "smart pendant" for lack > of a better way to describe it ? Although I don't see the sense of network connection between backend and frontend in hobby workshops, I would like to hear more from you. I'm always willing to learn. Here's a protocoll of someone trying network connection with linuxcnc and his failure ( - well, not his failure, but the failure by network concept ;) ): https://forum.linuxcnc.org/41-guis/36920-labview-ui-project-for-linuxcnc I believe, that putting a file into the ramdisk (which exists by default debian installations) is the fastest and easiest way for communication - even from realtimesystem to rest of the world. Any network communication could read from those files and do the conversion stuff - and for so, the extra time for conversion does not harm execution of backend (/realtime) processes. For me, that's flexible and performant at the same time. cheers Reinhard _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
