Using Axis-Remote over SSH

Sorry for the delay in responding.

The single quotes worked, and AXIS is definitely running, as I get a list of axis/emc-related processes running in the active processes list.

However, the 'glxinfo' command on my remote computer returns the following:

name of display: localhost:10.0
Error: couldn't find RGB GLX visual or fbconfig

The same command on my Linux machine returns a lot of info, but possibly importantly: "name of display: :0.0"

Does this conflict between display names matter?

I have used VNC a little, but what I want is the simplest way possible of controlling my machine (in my opinion, simple terminal commands).

As for emcrsh, it looks like that does what I'm looking for, although I do like having the AXIS GUI. Unless anyone has any more ideas I'll start working on trying to get emcrsh working. Thank you very much for the help!

it looks like glx not running on your mac X11 server -- you might check with knowledgeable mac folks to see if there is a way to support it

the localhost:10.0 is normal when using ssh -X

there may be some quirks but you can run more than one gui at the same time -- so you can have both axis and emcrsh

I got glx to work by removing a file on my Linux machine. axis-remote doesn't work, but now I do get something for 'glxinfo'.

I'm happy to go down the emcrsh route, but I'm confused as to how to be able to run both AXIS and emcrsh at the same time. The emcrsh manual says that I should change the DISPLAY parameter in my machine's .ini file to 'emcrsh'. But wouldn't this just push out AXIS?

> The emcrsh manual says that I should change the DISPLAY parameter in my
> machine's .ini file to 'emcrsh'. But wouldn't this just push out AXIS?

Note the next line from the emcrsh manpage:

> To use emcrsh in addition to a normal emc2 GUI, you can either start it at
> the end of your .hal file, or run it by hand in a terminal window.


There are multiple contexts for DISPLAY

For X11, there is an environmental variable named DISPLAY that indicates

hostname:displayno.screen

For emc, there is an ini file item named DISPLAY in a stanza also named DISPLAY, for example:

[DISPLAY]DISPLAY=axis

This names a startup gui that is used when emc is invoked by the standard startup script named emc.

Thank you very much for your help!

I came up with a primitive but functional solution to use axis-remote over ssh. You can read about the approach and download some code to implement the mdi mode here:

github.com/rbmadigan/axis-remote-ssh-fix...is_remote_client/src

comments and improvements are welcome.

Bruce

This works for me to a machine running LinuxCNC with
the axis gui displayed on that machine: (--help used
for testing):

The above requires machine_running_axis to have a deb
install of LinuxCNC so that axis-remote is in the
default path that includes /usr/bin

For a RIP build, one would need to specify the
specific location of axis-remote, for example:


I have /etc/ssh/sshd_config:X11Forwarding yes
but i dont think it matters since the command
above is not forwarding.