Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Robert Murphy
I realised my opinion would come to bite me in the foot as I was diagnosing the linuxcncrsh-tcp test. I did come to realise that yes remote GUI would have a place in an industrial setting. I would imagine if the protocol was simple enough and with tcp a mid to hi end microcontroller with a

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Reinhard
Hi, my answer was rejected yesterday, so I try to resend it ... On Sonntag, 3. Mai 2020, 16:17:46 CEST Johannes Fassotte wrote: > The name remote UI should be considered to mean that it is interfaced to > LinuxCNC using a network connection. This connection for most individuals > would likely be

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Johannes Fassotte
The slow update rate is likely a method issue and not an issue with network speed itself. Most networks can handle speeds of GB per second rates which is much much faster than actually required. Networks are used to stream all sorts of data these days. Lagging behind can indicate a buffer

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Gene Heskett
On Sunday 03 May 2020 10:17:46 Johannes Fassotte wrote: > The name remote UI should be considered to mean that it is interfaced > to LinuxCNC using a network connection. This connection for most > individuals would likely be via local host but it can be used remotely > if desired from other

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Jon Elson
On 05/03/2020 07:26 AM, Robert Murphy wrote: Machinekit, IMHO, seemed to be focused more towards the hobbyist who wants bells and whistles rather than an industrial\commercial scene. Well, no. A major focus was to support multiple instances of Machinekit working in the same physical space,

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Nicklas Karlsson
> Hi, > > On Sonntag, 3. Mai 2020, 10:43:12 CEST N wrote: > > Reading manual. "motion -- accepts NML motion commands" so I guees you want > > some of these commands to come from your hardware buttons? > > Well, my idea is to have hardware buttons for every command, so that the UI > is > just

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Johannes Fassotte
The name remote UI should be considered to mean that it is interfaced to LinuxCNC using a network connection. This connection for most individuals would likely be via local host but it can be used remotely if desired from other suitable devices. Such a interface adds flexibility and would

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Robert Murphy
I agree, I never saw the sense in a remote UI, other than all the "hipster\makers" want to control the world with their phones. Machinekit, IMHO, seemed to be focused more towards the hobbyist who wants bells and whistles rather than an industrial\commercial scene. Don't take this as having a go,

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Reinhard
Hi, On Sonntag, 3. Mai 2020, 10:43:12 CEST N wrote: > Reading manual. "motion -- accepts NML motion commands" so I guees you want > some of these commands to come from your hardware buttons? Well, my idea is to have hardware buttons for every command, so that the UI is just an infoboard. Don't

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Reinhard
Hi Daniel, > It seems some developer at machinekit did some good work there. > ... > ... are the best features in machinekit that are missing in linuxcnc. Hm, I don't think, that a remote ui is something important, that linuxcnc is missing. And I don't take the nml-layer for bad so that it

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread N
> 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

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Daniel Scheeren
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:

[Emc-developers] Installer "Vendor"

2020-05-03 Thread andy pugh
https://wiki.debian.org/Derivatives/Guidelines Should we be adding things to /etc/dpkg/origins ? -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper,

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread Reinhard
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,

Re: [Emc-developers] Third-Party GUIs

2020-05-03 Thread N
> Please don't ditch Axis. It's nice, clean & simple and I found it quite > intuitive to use. It works well for my hobby class 3 axis mill. Guess it do exactly what it should but have no other experience with other GUI for CNC machine. > I like the fact that there is a GUI included with