Is it possible to support remote scenarios for LinuxCNC

[summerlotus513]

I noticed that there is a framework QtQuickVcp on another derivative version of LinuxCNC (machinekit), with modules such as halltalk and mkwrapper, it is possible for me to remotely control my machines in the LAN on any platform. I have also tried it and it does meet some of my needs. I noticed that LinuxCNC seems to have no related content, or does not provide a framework similar to QtQuickVcp for our secondary development.
Is it possible to support QtQuickVcp or other forms of remote solutions in the future? I see that libnml seems to be supported, but IMHO, it is currently not easy to use in the remote control scenario, or it may be because my configuration method is incorrect.

[andypugh]

What do you want to do? Machinekit has better support for GUI and realtime on different CPUs, but there are other ways to remote control LinuxCNC, depending on where you want to draw the boundary.

[silopolis]

Le sam. 20 août 2022 à 12:56, andypugh ***@***.***> a écrit :

Machinekit has better support for GUI and realtime on different CPUs,

Could you elaborate please? We need a page somewhere to list and detail differences with MK, with a note about their backportability when they can be desirable. but there are other ways to remote control LinuxCNC, depending on where you

want to draw the boundary.

AFAIR, we don't have page in docs about ways to remote control LinuxCNC or split components on different CPUs. Just created #1949 and #1950 to gather these informations.

[andypugh]

Le sam. 20 août 2022 à 12:56, andypugh @.***> a écrit :
Machinekit has better support for GUI and realtime on different CPUs,
Could you elaborate please?

Machinekit decided to commit hard to the Beaglebone Black (The PRU's are very interesting). But it has lousy graphics performance so they worked on running motion / interp(?) on the BBB and GUIs on remote machines.

That's as much as I know. I ceased involvement in MK fairly early on, when it was made clear that my input was not welcome.

[smoe]

I have seen a raspberry pi configured for windows remote desktop - ah, here: https://www.youtube.com/watch?v=g-fzD8sEcIk

I would volunteer to add a respective description for our documentation.

[andypugh]

I just remembered: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Rockhopper_Web_Server
I am fairly sure that I remember seeing Charles(?) demonstrate an MPG on his smartphone that connected to a running LinuxCNC through rockhopper.
Note that it has been 9 years since that page was updated and bitrot might have set in.

[silopolis]

Le dim. 21 août 2022 à 03:39, andypugh ***@***.***> a écrit :

... they worked on running motion / interp(?) on the BBB and GUIs on remote machines.

Interesting! Can be valuable in this case as well as for clustering scenarios (like that guy working an integrex retrofit on Instagram with the idea of using one NC for each spindle/turret/head combo and another for sync/orchestration) That's as much as I know. I ceased involvement in MK fairly early on, when

it was made clear that my input was not welcome.

This is so sad to read... Anyway, where in the stack do these modifications happened and could these be backported? If you know the answers of course... @rene-dev maybe you have an idea?