How real time do you want the GUI? Is a few second lag behind the machines state ok? How about E-stop or Start/Stop from the UI? What's safe? 1 second max, 10 seconds? If you are milling while at the beach miles away does it matter? What problem are we solving?
On 03/20/2016 02:10 AM, Nicklas Karlsson wrote: > Then linuxcnc is split in two as in 1) and 2) above it is more or less done, > Why not gtk as now? > > >> >Another words just as you said except I'd drive the screen with some kind >> >of network protocol (like HTML or whatever) that would be wireless if the >> >user prefers that. > On Linux there are X11 but I expect there would be a special purpose protocol > between GUI and machine. In practice which buttons user pressed and values > back. High speed values like encoder values for hal scope would not be a > proble screen update is rather slow and a small delay would be a jerk on the > screen not the part. > >> >... > I plan to start looking at as soon as I get my first machines up and running. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
